-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation #44
Documentation #44
Conversation
See #45 for a list of open questions that should be included in the documentation. |
Assuming that Armin is going to be the one to address the questions in #45, and that we probably don't want to deal with having him to push his changes to my branch before merging, my thought is that we should merge this and then have Armin open a new PR when he has time to answer those questions. @arminrest does that make sense to you? If so I'll probably ask @aliciacanipe or @bsunnquist to take a quick look at these docs to look for spelling/grammar/glaring omissions, and then merge when they are happy. |
If you want to see the documentation on a webpage rather than just looking at text files, after you pull this branch, go into the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I just had some minor grammar and installation/setup instruction suggestions.
Thanks for the comments @bsunnquist! I think I addressed all of them, and I added in some clarifying text from Armin as well. If you're happy, could you hit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good to me!
This PR begins to add some basic coherent documentation in order to help the power users who are going to start playing with
jwst_reffiles
in the next week or so. There is still more that needs to be added, but hopefully I've covered the basics here.